Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #3139

/assign sebsoto

Attempts to fix an issue where Windows Server 2019 machines were not
having a running SSH server due to network instability.
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-56131 has been cloned as Jira Issue OCPBUGS-60774. Will retitle bug to link to clone.
/retitle [release-4.18] OCPBUGS-60774: Retry SSH server initialization

In response to this:

This is an automated cherry-pick of #3139

/assign sebsoto

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot changed the title [release-4.18] OCPBUGS-56131: Retry SSH server initialization [release-4.18] OCPBUGS-60774: Retry SSH server initialization Aug 21, 2025
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Aug 21, 2025
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-60774, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.z) matches configured target version for branch (4.18.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-56131 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-56131 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.z
  • bug has dependents

Requesting review from QA contact:
/cc @rrasouli

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This is an automated cherry-pick of #3139

/assign sebsoto

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@jrvaldes
Copy link
Contributor

/retest-required

@jrvaldes
Copy link
Contributor

/lgtm

@jrvaldes
Copy link
Contributor

/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 26, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 26, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jrvaldes, openshift-cherrypick-robot

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 26, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 9c20667 and 2 for PR HEAD 9d528b4 in total

4 similar comments
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 9c20667 and 2 for PR HEAD 9d528b4 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 9c20667 and 2 for PR HEAD 9d528b4 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 9c20667 and 2 for PR HEAD 9d528b4 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 9c20667 and 2 for PR HEAD 9d528b4 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 7c46544 and 1 for PR HEAD 9d528b4 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD b239f57 and 0 for PR HEAD 9d528b4 in total

@openshift-ci-robot
Copy link

/hold

Revision 9d528b4 was retested 3 times: holding

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 29, 2025
@sebsoto
Copy link
Contributor

sebsoto commented Sep 2, 2025

/override ci/prow/vsphere-disconnected-e2e-operator

@sebsoto
Copy link
Contributor

sebsoto commented Sep 2, 2025

/cherrypick release-4.17 release-4.16

@openshift-cherrypick-robot
Copy link
Author

@sebsoto: once the present PR merges, I will cherry-pick it on top of release-4.17 in a new PR and assign it to you.

In response to this:

/cherrypick release-4.17 release-4.16

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 2, 2025

@sebsoto: Overrode contexts on behalf of sebsoto: ci/prow/vsphere-disconnected-e2e-operator

In response to this:

/override ci/prow/vsphere-disconnected-e2e-operator

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@sebsoto
Copy link
Contributor

sebsoto commented Sep 2, 2025

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 2, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 23a196b and 2 for PR HEAD 9d528b4 in total

3 similar comments
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 23a196b and 2 for PR HEAD 9d528b4 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 23a196b and 2 for PR HEAD 9d528b4 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 23a196b and 2 for PR HEAD 9d528b4 in total

@jrvaldes
Copy link
Contributor

jrvaldes commented Sep 3, 2025

/override ci/prow/platform-none-vsphere-e2e-operator

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 3, 2025

@jrvaldes: Overrode contexts on behalf of jrvaldes: ci/prow/platform-none-vsphere-e2e-operator

In response to this:

/override ci/prow/platform-none-vsphere-e2e-operator

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-merge-bot openshift-merge-bot bot merged commit 0742199 into openshift:release-4.18 Sep 3, 2025
18 checks passed
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-60774: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-60774 has been moved to the MODIFIED state.

In response to this:

This is an automated cherry-pick of #3139

/assign sebsoto

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-cherrypick-robot
Copy link
Author

@sebsoto: new pull request created: #3256

In response to this:

/cherrypick release-4.17 release-4.16

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants